Mastering Puppet 5 by Ryan Russell-Yates

Author:Ryan Russell-Yates
Language: eng
Format: epub
Tags: COM059000 - COMPUTERS / Computer Engineering, COM043000 - COMPUTERS / Networking / General, COM051000 - COMPUTERS / Programming / General
Publisher: Packt Publishing
Published: 2018-09-29T05:23:19+00:00

Summary

We started this chapter by detailing what makes for a good workflow. Much of the workflow becomes easier when combined with continuous integration and continuous delivery strategies, which will be covered in the next chapter. We'll expand upon the RSpec tests built by the Puppet PDK, and we'll discuss acceptance test strategies. We'll also cover some new workflows and tools to provide more immediate feedback during the development of Puppet code and manifests.

Continuous Integration

Continuous Integration as a practice is ensuring that each time code is committed, it is built and tested the same way consistently. We use Continuous Integration systems to automate this practice, making it practical for use on every commit. Some Continuous Integration pipelines eventually evolve into Continuous Delivery or Continuous Deployment pipelines. The key difference between Continuous Integration and delivery is that delivery ensures that every time code is committed, it is also wrapped up (or packaged) and delivered to the doorstep of the server it needs to run on. Continuous Delivery requires the ability to deploy your entire infrastructure and application consistently with a single orchestration command. Continuous Deployment requires an end-to-end suite of tests for every component in your infrastructure, but is the simple task of automating that single orchestration command when every test passes.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.